home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000119_news@columbia.edu_Wed Aug 9 09:42:37 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
5KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA16420
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 9 Aug 1995 20:53:36 -0400
Received: by apakabar.cc.columbia.edu id AA01163
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 9 Aug 1995 20:53:34 -0400
Path: news.columbia.edu!sol.ctr.columbia.edu!news.msfc.nasa.gov!newsfeed.internetmci.com!news.mathworks.com!news.kei.com!nntp.et.byu.edu!news.provo.novell.com!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: MSKermit over IP connection
Message-Id: <1995Aug9.154237.58499@cc.usu.edu>
Date: 9 Aug 95 15:42:37 MDT
References: <4073r0$ijs@linda.teleport.com> <1995Aug8.082408.58352@cc.usu.edu> <409uom$apq@kelly.teleport.com>
Organization: Utah State University
Lines: 84
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <409uom$apq@kelly.teleport.com>, sysone@teleport.com (FIGHT THE POWER) writes:
> I'll _try_ to recast this coherently... :-)
>
> Joe D. wrote:
>
> # I'm not sure I follow all the details above, but let me take a
> #stab at matters.
> # SLIP is a point to point transport mechanism with only two stations
> #on the wire: this end and "the other end". There is no ARP-ing involved
> #since ARP is a way of finding one of many stations on the same broadcast
> #medium (and a serial link isn't a broadcast medium). CSLIPPER is a SLIP
> #Packet Driver.
>
> Right... I'm thinking of the connection as running
> something like this:
>
> [My DOS app] -> [SLIP or PPP client] -> [Serial card] ->
> [My modem] -> [Telephone network] -> [Server's modem] ->
> [Server's port] -> [SLIP or PPP server] -> [Server's LAN] ->
> [LAN's TCP/IP gateway] -> Internet stuff...
>
> # Given a point to point architecture "the other end" is responsible
> #for transporting packets to far away places, and hence it is both a host
> #and the gateway. Figuring out what to do with packets not addressed to it
> #is a problem that other end has to deal with. I have no idea of how you
> #have the Cisco boxes configured. In any case, SLIP has no notion of routing,
>
> I don't know about the Ciscos' configurations either,
> although I can get some information from the server prompt using
> the 'show' command with various extensions. I have asked the
> support office here re the manuals... which they couldn't locate!
>
> #gateway, or ARP. Any routing which does occur is a pleasant side effect
> #of "the other end."
> #
> I'm thinking that the server, attempting to link me to
> the Net, can't resolve the gateway's IP address into a valid
> Ethernet address, and sends some message to this effect back to
> the client. Since the client (DOS Kermit in this case) is
> attached to the server via SLIP/PPP, the message is passed over
> the link layer back to my SLIP/PPP driver, which complains to
> Kermit; the link layer has nothing to do with all this beyond
> hauling datagrams back and forth.
>
> All this is based on my exceedingly limited knowledge of
> networking of course. I'm probably out to lunch on some of it.
>
> # EtherPPP is the MERIT item, I presume. Honestly, I have never been
> #able to get that program to work in any way; it always hangs my machine as
> #it starts up. Thus I have nothing useful to suggest for it.
> #
> Yup, configuring EtherPPP is a unique experience. It
> works great now that I've figured out the settings my machine
> likes. But that doesn't mean I've found a configuration which
> would work everywhere. To return to the topic, the ARP problem
> appears to occur independent of the driver (I have tried two
> EtherPPP releases as well as the {,C}Slipper drivers). With the
> earlier Kermit no problem. With the recent Kermit, the ARP error
> is returned.
>
> # Adding to my confusion on your report is "name resolution doesn't
> #seem to be a problem." If the nameserver is far away, in the SLIP sense,
> #then that is no different than trying to reach another machine far away.
> #
> Right. An inadvertent red herring on my part...
>
> I don't know if what I have added is helpful in
> diagnosing the problem. I would be more than happy to mail in
> session transcripts, config files &c. if this would help. I
> suppose I've used enough bandwidth on this question at any rate.
>
> Thanks...
-------------
I fired up CSLIPPER with no command line arguments so it behaved
as a straight SLIP Packet Driver. I ran MS-DOS Kermit over it to our modem
pool (Telebit Netblazers) and used both domain name servers and far away
machine addresses, all with no difficulty. I set the MSK TCP/IP IP address
from the text line the modem pool gave me upon starting SLIP there.
I notice that CSLIPPER has an ARP/IP Ethernet faker option. Without
knowing in detail what it does I would recommend not activating that faker
with Kermit.
From this I am tempted to conclude that the IP environment outside
of Kermit is causing the difficulties you note.
Joe D.